N4 supports the Saudi Manifest message as per the specification document version 3.0 received from Red Sea Gateway Tterminals(RSGT) since the feature is primarily developed for RSGT. A new message class "SAUDIMANIFEST" has been added in N4.
Saudi Manifest Order is a Flatfile Edi transferred from Shipping Agents to Terminals in Saudi region. This EDI file contains list of containers, BLs, BL Item details in a vessel. This Edi message can be for New, Update, Delete messages.
As per Saudi EDI standard, at least one BL is expected. Each BL should have at least 1 BL Item. Currently we support Import and Export manifest.
The Shipping Agent advises the terminal of the list of Containers, BLs, BL Items and their relationships. The system should create all this data in N4 after applying all the business validations.
Oil is not supported. In cargo, Bulk cargo is currently unsupported.
A Saudi Manifest message may contain the following information in same order:
Saudi Manifest Header - Contains vessel visit, manifest message detail etc..
Routing Information
Containers
Bill Of Ladings
BL Items
This guideline document specifies on how the Saudi Manifest EDI message is implemented and how N4 can be configured to process this particular message.
SAUDIMANIFEST30 Inbound Supported Segments
Container, BL, BL Item are separate individual EDI transactions and therefore they don't communicate between one another while posting.
(ex: If BL not created because of a error, BL Item will know it. It will say BL sequence number not found in system)
Oil/Bulk cargo are not supported as on now.
A BL will be deleted only if all BL Items are deleted. So delete message for BL doesn't make any difference.
A container will be retired if a delete message is posted for a container.
SAUIDMANIFEST Inbound - Message Functions
Saudi Manifest has a message function (N-New/U-Update/D-Delete) in all segments. But message functions are applicable only for containers, BLs, and BL Items.
Container
Container (New): Use the Unit if it already exists and update the sequence number, otherwise create a Unit.
Container (Update): Use the Unit if it already exists with given sequence number, otherwise Error out.
Container (Delete): Delete the Unit matching the sequence number.
Bill of Lading
BL (New): Create a new BL, Error out if the sequence number already exists.
BL (Update): Update the existing BL having a given sequence number. Error out if the sequence number is not found.
BL (Delete): Don't do anything as BL gets deleted automatically when all BL Items are deleted.
BL Item
BL Item(New): Create a new BL Item and Cargo Lot. Error out if the sequence number already exists.
BL Item(Update): Update existing BL Item having given sequence number. Error out if the sequence number is not found.
BL Item(Delete): Delete BL Item, remove Unit from Cargo Lot, delete Cargo Lot, and if there is no more BL Items on this BL, then delete the BL
Custom Map for Saudi Manifest Inbound
Since the Saudi manifest is a flat file, it cannot be processed as such in N4. So a new Xml schema (saudimanifest.xsd) has been defined for SAUDIMANIFEST message class and a flat file Saudi manifest message has to be converted to this particular xml structure.
For this, a new OpenText Output Transformation (formerly Xenos) map(saudimanifest_30.mgt) has been developed to transform the Saudi manifest flat file to N4 standard xml format during runtime.
Note: The custom map is not a built-in map which means there won't be a Message Type (in Message Types UI) in N4 with this map and message class SAUDIMANIFEST. Customers that want to use the Saudi manifest need to get the latest map from PS and maintain it themselves if any customization is done.
Special Handling
Entity Type
As the Saudi manifest contains information various entities, such as BL, BL Item and Container, etc., a separate attribute is present in Navis standard xml (saudimanifest.xsd) to specify the type of entity to be processed in N4.
Possible values for entity type field are:
CN : Container
BL : Bill Of Lading
BLITEM : BL Item
This attribute is used for following purpose:
to control the code flow
to validate the integrity of the transformed xml - for example, if the entity type is BL, the transformed xml should contain BL information.
to resolve the keywords specific to an entity
Sequence Numbers
Since the Saudi Manifest is a flat file EDI, it has sequence numbers at each segment level that are used to refer in further update messages for the same entity and message. The sequence numbers are unique in a particular message but not across messages. So to make it unique across messages, in N4, in addition to the sequence number of a particular entity, information such as manifest number and date are used as well.
In N4, once the Saudi manifest flat file is transformed to Navis standard xml, the sequence number of various entity will be concatenation of many values.
Hard Coded EDI Trading Partner
In N4, to process an inbound EDI, an Edi Session needs to be created, which in turn needs a EDI Trading Partner. According to ANSI & EDIFACT standards, the EDI Trading partner refers to the sender of the EDI message. But Saudi manifest flat file does not have such information at all.
So, as of now, for the Saudi manifest developed for Saudi EDI, the EDI trading partner name is hard coded as "SAUDICUSTOMS". For customers that want to use a different partner name, the OpenText Output Transformation (formerly Xenos) map (saudimanifest.mgt) has to be customized with the required partner name.
How to Configure N4 for Saudi Manifest Inbound?
To process Saudi Manifest, the following set up has to be done:
Message Type should be created with Message Class as "SAUDIMANIFEST" and Standard as "FLATFILE".
A Message map should be created under the message type direction as Receive, import the map file "saudimanifest_30.mgt" and dictionary file "saudimanifest.fxd".
In the EDI Configuration UI, create a EDI Trading Partner.
Create an EDI Mailbox with direction as Receive.
Create an EDI Session with following attributes:
Message Class - SAUDIMANIFEST
Direction - Receive
Map - Select Map id as created under Message Type
Message Delimiter - \n
Posting Logic for Saudi Manifest Inbound
In this Section:
Posting logic for container NEW (N) 1
Posting logic for container UPDATE (U) 1
Posting logic for container DELETE (D) 1
Posting logic for BL NEW (N) 1
Posting logic for BL UPDATE (U) 1
Posting logic for BL DELETE (D) 1
Posting logic for BL Item NEW (N) 1
Posting logic for BL Item UPDATE (U) 1
Posting logic for BL Item DELETE (D) 1
Posting logic for container NEW (N)
When a Saudi manifest message is posted for a container with N message type, following are the implications :
Error out if the unit sequence number already exists.
If unit already exists, take that unit, otherwise create a new unit.
Update unit attributes from the EDI message.
Posting logic for container UPDATE (U)
When a Saudi manifest message is posted for a container with U message type, following are the implications :
Error out if the unit sequence number does't exist.
Update unit attributes from the EDI message.
Posting logic for container DELETE (D)
When a Saudi manifest message is posted for a container with D message type, following are the implications :
Error out if the unit sequence number does't exist.
Error out if the unit is in yard or any state after yard.
Retire the unit.
When a Saudi manifest message is posted for a BL with N message type, following are the implications :
Error out if the BL sequence number already exists.
If BL already exists, take that BL, otherwise create a new BL with a given sequence number.
Update BL details from the EDI message.
Posting logic for BL UPDATE (U)
When a Saudi manifest message is posted for a BL with U message type, following are the implications :
Error out if the BL sequence number doesn't exist.
Update BL details from the EDI message.
Posting logic for BL DELETE (D)
When a Saudi manifest message is posted for a BL with D message type, following are the implications :
Post completes successfully without any action. (BL will be deleted once all BL Items are deleted).
Posting logic for BL Item NEW (N)
When a Saudi manifest message is posted for a BL Item with N message type, following are the implications:
Error out if the BL Item sequence number already exists.
Update the BL Item and cargoLot details from the EDI message.
Attach the referred unit to this cargoLot.
Attach referred BL Item to this BL.
When posting the ediCargoLot element, if the ediCargoLotUnit element is not provided, the posting is not stopped.
Posting logic for BL Item UPDATE (U)
When a Saudi manifest message is posted for a BL Item with U message type, following are the implications :
Error out if the BL Item sequence number doesn't exist.
Update the BL Item and cargoLot details from the EDI message.
Attach the referred unit to this cargoLot.
Posting logic for BL Item DELETE (D)
When a Saudi manifest message is posted for a BL Item with D message type, following are the implications :
Error out if the BL Item sequence number doesn't exist.
Get Unit, BL and BL Item from CargoLot.
Remove the Unit link from the cargo lot.
Delete the cargo lot and BL Item.
If there are no more BL Items in this BL, delete the BL.
Remove the link between BL and Unit.
Saudi Manifest Inbound Samples
New
SAUMAFH100~N~1~2~20040708000002~20040705~101630~KOTA GUNAWAN~???? ??????~~~~~20~AE~3344556~C163E~SAJED~1~20040807132300~20040818173000~20040812~1355~1356~TEST FOR DIRECT SHIPMENT~30~22
SAUMAFD150~N~1~SG~SGSIN~1~FROM SINGAPORE
SAUMAFD150~N~2~SA~SAJED~1~To Jeddah
SAUMAFD200~N~61~1355~1356~DRY~2591~2438~40~BLJU 1231231~536341~536342~536343~1~4200~8080~0~1~2~3~CEL~MRK~NOTES
SAUMAFD300~N~61~2~LONA123123~0~SMN~~~JOHN REEKS TRADING PTE LTD???????? ???????? ????????~SAUDI CARS INDUSTRIES~P.O. BOX 6535 DAMMAM POSTAL CODE 31452 SAUDI ARABIA~6212234~8593090~6535~31452~1355~1356~USOAK~1~TH~SARUH~4~8080~120.0~1~1~GENERAL REMARKS~RM1
SAUMAFD350~N~61~61~45.0~PK~12~PC~8080~123.0~5~2~0~2~8~HIGHLY EXPLOSIVE CHEMICALS~???? ???????? ????? ?MARKS NO.711?1
Update
SAUMAFH100~U~1~1~20040708000002~20040705~101630~KOTA GUNAWAN~???? ??????~~~~~20~AE~3344556~C163E~SAJED~1~20040807132300~20040818173000~20040812~1355~1356~TEST FOR DIRECT SHIPMENT~30~22
SAUMAFD150~U~1~SG~SGSIN~1~FROM SINGAPORE
SAUMAFD150~U~2~SA~SAJED~1~To Jeddah
SAUMAFD200~U~11~1112~1113~VENTILATED~2591~2438~40~BLJU 4200111~126341~126342~126343~2~4500~7080~0~4~5~6~CEL~MRNO~container has hole
SAUMAFD300~U~11~1~LONA438111~0~SMN~~~MANNAR & CO PTE LTD???????? ???????? ????????~FINUX TOILET CLEANER INDUSTRIES~P.O. BOX 13 XXX POSTAL CODE 123 SAUDI ARABIA~12312222~34343223~6535~3234234~32223~32224~USOAK~1~XX~SARUH~4~8080~100.0~1~1~GEN REM~RM1
SAUMAFD350~U~11~11~55~SE~8~PC~6080~321~11~2~0~2~9~POTTU PATTASU~???? ???????? ????? ?MARKS NO.222?1
Delete
SAUMAFH100~D~1~2~20040708000002~20040705~101630~KOTA GUNAWAN~???? ??????~~~~~20~AE~3344556~C163E~SAJED~1~20040807132300~20040818173000~20040812~1355~1356~TEST FOR DIRECT SHIPMENT~30~22
SAUMAFD150~D~1~SG~SGSIN~1~FROM SINGAPORE
SAUMAFD150~D~2~SA~SAJED~1~To Jeddah
SAUMAFD200~D~21~1355~1356~DRY~2591~2438~40~BLJU 4200222~536341~536342~536343~1~4200~8080~0~1~2~3~XX~MRK~NOTES
SAUMAFD300~D~21~2~LONA438222~0~SMN~~~JOHN REEKS TRADING PTE LTD???????? ???????? ????????~SAUDI CARS INDUSTRIES~P.O. BOX 6535 DAMMAM POSTAL CODE 31452 SAUDI ARABIA~6212234~8593090~6535~31452~1355~1356~USOAK~1~TH~SARUH~4~8080~50~1~1~GENERAL REMARKS~RM1
SAUMAFD350~D~21~21~50~PK~12~PC~8080~123~5~2~0~2~8~HIGHLY EXPLOSIVE CHEMICALS~???? ???????? ????? ?MARKS NO.711?1
Multiple Container Reference
SAUMAFH100~N~1~2~20040708000002~20040705~101630~KOTA GUNAWAN~???? ??????~~~~~20~AE~3344556~C163E~SAJED~1~20040807132300~20040818173000~20040812~1355~1356~TEST FOR DIRECT SHIPMENT~30~22
SAUMAFD150~N~1~SG~SGSIN~1~FROM SINGAPORE
SAUMAFD150~N~2~SA~SAJED~1~To Jeddah
SAUMAFD200~N~1~1355~1356~DRY~2591~2438~40~BLJU 4200514~536341~536342~536343~1~4200~8080~0~1~2~3~XX~MRK~NOTES
SAUMAFD200~N~2~1355~1356~DRY~2591~2438~40~BLJU 4200600~536341~536342~536343~1~4200~8080~0~1~2~3~XX~MRK~NOTES
SAUMAFD300~N~1~2~LONA438376~0~SMN~~~JOHN REEKS TRADING PTE LTD???????? ???????? ????????~SAUDI CARS INDUSTRIES~P.O. BOX 6535 DAMMAM POSTAL CODE 31452 SAUDI ARABIA~6212234~8593090~6535~31452~1355~1356~USOAK~1~TH~SARUH~4~8080~50~1~1~GENERAL REMARKS~RM1
SAUMAFD350~N~1~1~50~PK~12~PC~8080~123~5~2~0~2~8~HIGHLY EXPLOSIVE CHEMICALS~???? ???????? ????? ?MARKS NO.711?1
SAUMAFD300~N~2~2~LONA438377~0~SMN~~~JOHN REEKS TRADING PTE LTD???????? ???????? ????????~SAUDI CARS INDUSTRIES~P.O. BOX 6535 DAMMAM POSTAL CODE 31452 SAUDI ARABIA~6212234~8593090~6535~31452~1355~1356~USOAK~1~TH~SARUH~4~8080~50~1~1~GENERAL REMARKS~RM1
SAUMAFD350~N~1~2~50~PK~12~PC~8080~123~5~2~0~2~8~HIGHLY EXPLOSIVE CHEMICALS~???? ???????? ????? ?MARKS NO.711?1
SAUMAFD350~N~2~1~50~PK~12~PC~8080~123~5~2~0~2~8~HIGHLY EXPLOSIVE CHEMICALS~???? ???????? ????? ?MARKS NO.711?1
SAUMAFD350~N~3~2~50~PK~12~PC~8080~123~5~2~0~2~8~HIGHLY EXPLOSIVE CHEMICALS~???? ???????? ????? ?MARKS NO.711?1